-
Notifications
You must be signed in to change notification settings - Fork 214
Bump CAPI to v1.10.2 #1459
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump CAPI to v1.10.2 #1459
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Welcome @tamalsaha! |
Hi @tamalsaha. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@tamalsaha - please can you remove the vendor folder from this PR. |
Removed vendor folder @richardcase . PTAL. |
@@ -33,36 +35,44 @@ var clusterlog = logf.Log.WithName("gcpcluster-resource") | |||
|
|||
// SetupWebhookWithManager sets up and registers the webhook with the manager. | |||
func (c *GCPCluster) SetupWebhookWithManager(mgr ctrl.Manager) error { | |||
w := new(gcpClusterWebhook) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we move the webhooks to internal/webhooks
so that we start brining the structure in line with upstream CAPI and also kubebuilder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sounds reasonable. But can this be done in a separate pr (preferrably by project maintainers), as this will look like a lot of change in the pr and mask the actual change needed to make things work with the kubebuilder api breakage?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah +1 for doing this, but probably best to do it in a follow up PR to avoid polluting this one
Hey @tamalsaha Now that a complete Go dependecy bump PR has merged from @cpanato #1449 would you be able to rebase yours on top of the latest main. This should cover part of @richardcase comment here: #1459 (comment) Also it looks like the CAPI v1.10.0-rc.0 is out, so it would be nice to use that instead of beta.0. |
b824d79
to
4bee5aa
Compare
/ok-to-test |
I guess we'll have to wait for the next CAPI patch release to have this fixed: kubernetes-sigs/cluster-api#12180. Is that correct? |
Yes correct @salasberryfin |
New error: failed to read "cluster-template-topology.yaml" from provider's repository "infrastructure-gcp": failed to read file "/logs/artifacts/repository/infrastructure-gcp/v1.10.99/cluster-template-topology.yaml" from local release v1.10.99: stat /logs/artifacts/repository/infrastructure-gcp/v1.10.99/cluster-template-topology.yaml: no such file or directory |
It looks like you fixed that thanks |
@tamalsaha a couple of things to fix:
|
"admission webhook "validation.cluster.cluster.x-k8s.io" denied the request: Cluster.cluster.x-k8s.io "capg-e2e-yoj5vd" is invalid: [spec.infrastructureRef: Forbidden: cannot be removed, spec.controlPlaneRef: Forbidden: cannot be removed]" |
@tamalsaha yes, this is what I was asking @salasberryfin about, as he last touched that area of tests. |
@tamalsaha, @salasberryfin replied here, https://kubernetes.slack.com/archives/C01D1RFEN9G/p1748331885434999?thread_ts=1745836188.671049&cid=C01D1RFEN9G would you be able to try that out? Thanks! |
cc. @tamalsaha |
Signed-off-by: Tamal Saha <[email protected]>
Signed-off-by: Carlos Salas <[email protected]>
@damdo Done. |
@tamalsaha: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/test pull-cluster-api-provider-gcp-conformance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
e2e, capi-e2e and conformance all passed
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damdo, tamalsaha The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Added my approval @richardcase @salasberryfin @cpanato are you able to LGTM if you are happy with it? Thanks! |
Thanks a lot @tamalsaha @damdo. /lgtm |
Awesome, thanks a ton @tamalsaha !! |
What type of PR is this?
What this PR does / why we need it:
I fixed the validator and defaulter interface broken by controller-runtime.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: